Downgrade Lambdaworks to 0.11.0 #161
Open
+38
−24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Downgrades Lambdaworks version from 0.12.0 to 0.11.0 since both supports QM31 but the latter doesn't check that a point is in the curve when creating it.
Pull Request type
Performance improvement.
What is the current behavior?
Run:
Here are the results of Pedersen benchmarks, tested in Apple M3 Pro, macOS Sequoia 15.6.1, 18 GB RAM:
rev
5774f89bccf6b5ed772072244ad2a17e604ada55
(base):rev
ee5743bfc1a91638150029b615fa21fdb6a3292e
(head):Resolves: #NA
What is the new behavior?
0.3.0 showed a performance regression in Pedersen, making them ~120% slower. This PR restores Pedersen performance by downgrading Lambdaworks version.
At the moment, I preserved the QM31 API to avoid merging a breaking change. For instance, this function returns a
Result
but it will always return theOk
variant. However, I'm open for suggestions to change the API for simplification.Does this introduce a breaking change?
No